r? @Mark-Simulacrum

(rustbot has picked a reviewer for you, use r? to override)

...of course I forget to r? @ghost

Failed to set assignee to ghost: invalid assignee

Note: Only org members, users with write permissions, or people who have commented on the PR may be assigned.

(asking for my own curiosity, not really suggesting anything) is there a need to remove all the dist-mips folders? It seems likely enough that they may be reenabled at some point, so maybe worth keeping them in tree with history and all? Or moved to a different directory if some tool automatically looks for the dist-x dirs

git preserves all history, if one needs to be a git historian.

Given that commits can also be easily reverted, I have received a recommendation that we should in fact remove these builders immediately, rather than waiting, as the burden has made it so essentially every PR merged lately has had one bors retry (...averaged). Which is fine by me, assuming that I did this correctly and everyone's on board. I will remove the "formally change the platform support page" commit to another PR.

But there some folder with promising name https://github.com/rust-lang/rust/tree/master/src/ci/docker/host-x86_64/disabled

I don't think this should touch anything more than the CI configuration.

So just 634f952 ?

https://rust-lang.zulipchat.com/#narrow/stream/233931-t-compiler.2Fmajor-changes/topic/Drop.20MIPS.20to.20tier.203.20compiler-team.23648/near/372165737:

I think an easy workaround is to land now, and revert on (future) beta. We can get past the bugs with a couple retries on the beta + stable compiler builds, but this fixes most folks builds now.

@bors r+ p=50 rollup=never

📌 Commit 634f952 has been approved by jyn514

It is now in the queue for this repository.

⌛ Testing commit 634f952 with merge 2c2f5cf020a890a48e8b4ff87ccad8cfdf118be1...

@bors ping

😪 I'm awake I'm awake

@bors treeclosed=100 the tree is fucked up because of a raced try-build and auto merge in #113213

gonna bump this auto build out of the queue, hope that's the right step here to make sure things don't get worse :(

@bors retry

(haha, bors probably wouldn't have even merged 634f952 because it's not a fast forward.)

@bors p=50
@bors retry

^^

@bors r- p=50

I think this can resume build now, thanks @Mark-Simulacrum for fixing the tree.

@bors r=jyn514
@bors treeclosed-

📌 Commit 634f952 has been approved by jyn514

It is now in the queue for this repository.

🌲 The tree is currently closed for pull requests below priority 100. This pull request will be tested once the tree is reopened.

⌛ Testing commit 634f952 with merge 9e4e584...

The merge looks correct

The job armhf-gnu failed! Check out the build log: (web) (plain)

curl: (22) The requested URL returned error: 404 

error: failed to download llvm from ci

    help: old builds get deleted after a certain time
    help: if trying to compile an old commit of rustc, disable `download-ci-llvm` in config.toml:
    [llvm]
    download-ci-llvm = false
    
Build completed unsuccessfully in 0:00:00

Or not?

Actually, that looks like a previous auto-merge, not this one.

#113274 (comment)

should this retry then?

No need -- it's merging successfully in https://github.com/rust-lang-ci/rust/actions/runs/5457834781

Weird.

☀️ Test successful - checks-actions
Approved by: jyn514
Pushing 9e4e584 to master...

Finished benchmarking commit (9e4e584): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 653.659s -> 653.846s (0.03%)